-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[DOC] Document search API #5521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
42b935d to
f3f86db
Compare
f3f86db to
ca756c3
Compare
|
Add Comprehensive Documentation for Cloud Search API This PR introduces extensive documentation for the new Search API within the Chroma Cloud section. The changes add a full set of docs pages covering the API's overview, filtering, ranking, hybrid search (RRF), limit/selection, batch operations, migration strategies, practical examples, as well as a sidebar reorganization to include a dedicated Search API group. Existing documentation is also updated with references and contextual callouts to guide users to the new Search API where relevant. Key Changes• Added new documentation pages under Affected Areas• This summary was automatically generated by @propel-code-bot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of the TS examples use type any mostly for collections. We have the Collection type that can be used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - pushed some changes. Recommend addressing @itaismith's feedback before merging.
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytestfor python,yarn testfor js,cargo testfor rustMigration plan
Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?
Observability plan
What is the plan to instrument and monitor this change?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the _docs section?_